Weekly tasks or assignments (Individual or Group Projects) will be due by Monday and late submissions will be assigned a...

Weekly tasks or assignments (Individual or Group Projects) will be due by Monday and late submissions will be assigned a late penalty in accordance with the late penalty policy found in the syllabus. NOTE: All submission posting times are based on midnight Central Time.

In the next few weeks you will be working on developing your Key Assignment Project. The Key Assignment will be a Business Case that will consist of the following components:

• Section 1 – Overview of Company and Client Business Case
• Section 2 - Application Requirement Elicitation Strategy 
• Section 3 - System Components and Design Requirements
• Section 4- Methodology for Application Development Process
• Section 5 - Complete Features and Trade-off Analysis
• Section 6 - Milestones and Deliverables based on Date and Dependencies
• Section 7 - System Architecture Aligned with System Requirements
• Section 8 - Technical Design Document
• Section 9 – Design Review Checklist
• Section 10 – Testing and Deployment

IMPORTANT NOTE: For weeks 1-4, you will be participating in small group discussion, making project decisions as a team but completing individual assignment. Each student will have the option of sharing components of their assignment with other team members. However, you are not required to do so and may opt to work individually. Even if you decide to share components with others, you must submit individual deliverables at the end of each unit.

In week 5 you will complete the new sections, make all suggested modification based on your instructor’s feedback and add additional input from group member's feedback and additional discussion. You will then combine all previous weekly submissions and submit your final project deliverable.

Group Discussion

Section 1 – Overview of Company and Client Business Case

As a group, hold a discussion and make a decision on a business case that will require the development and deployment of an IT Network System Application for any organization. As an idea, the Business Case could be but not limited to:

• The development of a custom accounting application for an accounting firm
• The development of a Customer Service Application for a store
• Student Information System for a small university
• Or any other similar solution requirements

As a group determine the following:

• Create a name for your company and a profile for your company
  • What is your company’s expertise?
  • Ensure that the expertise matches the skill sets required for the business case you have chosen 
• Client Case Overview
  • What client business case did you choose and why?
  • How does your company expertise match your client’s needs?
• Client Application Solution
  • Based on the case you have chosen, what do you believe is the application solution? Why? 

Section 2 – Application Requirement Elicitation and Strategy

Before you are able to work on the development of a solution you must have a clear understanding of the customers’ needs.

As a group discuss and determine the following:

• How will requirement elicitation be conducted by your team?
• Who will be the main stakeholder that you will be eliciting information from? 
• What questions need to be answered and why?
• How will you implement your elicitation strategy?

Section 3 - System Components and Design Requirements

As a group decide and discuss the following:

• Based on the elicitation results, finalize the system components and design requirements that are needed for your business case.
• Does the design solution support all the customer needs?
• Provide specifics that the proposed application should address

Based on the requirements, each individual will tackle the weekly deliverables. However, students can decide to share the work from various components of their project with each other. If this is the approach the group will use, each individual’s work must be cohesive to what other members are developing considering that the individual efforts will be combined across components. 

Section 4- Methodology for Application Development Process

 As a group, complete the following:

• Choose a system development methodology for your project.
• The methodology chosen should align with achieving the overall objective of your business case.

Individual Deliverables

Based on the discussions and the information gathered, start your business case. This will become the Key Assignment. Each of the following sections should be at least 1 page:

Section 1 – Overview of Company and Business Case

• Your group’s company name and profile
• Client Case Overview
• Client Application Solution

Section 2 – Application Requirement Elicitation and Strategy

Based on the group discussion, complete the following:

• What elicitation strategy you will implement?
• Who is the target audience?
• What questions need to be answered and why?
• Based on the implementation of your elicitation strategy, how did your application requirements change? Why?

Section 3 - System Components and Design Requirements

Leveraging the information gathered from the requirements elicitation process, complete the following specific to the system component you have been assigned:

• Develop a document that clearly identifies the system component and design requirements meeting the client’s need.

Section 4- Methodology for Application Development Process

• What System Development Methodology was chosen and why?
• How will this methodology be leveraged in this application solution? 
• How did this differ from what you originally discussed in the discussion board?
• Do you agree with the methodology chosen? Why or why not?
• What are the benefits and constraints of the methodology specific to the system component you are working on?

The template document should follow this format:

• Business Document Shell
• Use Microsoft Word
• Title Page
  • Course number and name
  • Project name
  • Student name
  • Team Number and Members
  • Date
• Table of Contents
  • Use auto-generated TOC.
  • Separate page
  • Maximum of three levels deep
  • Be sure to update the fields of the TOC so it is up-to-date before submitting your project.
• Section Headings (create each heading on a new page with TBD as content except for sections listed under New Content below)
  • Section 1 – Overview of Company and Client Business Case
  • Section 2 - Application Requirement Elicitation Strategy 
  • Section 3 - System Components and Design Requirements
  • Section 4- Methodology for Application Development Process
  • Section 5 - Complete Features and Trade-off Analysis
  • Section 6 - Milestones and Deliverables
  • Section 7 - System Architecture Aligned with System Requirements
  • Section 8 - Technical Design Document
  • Section 9 – Design Review Checklist
  • Section 10 – Testing and Deployment